-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix ledger range calculation #217
Conversation
…etHealth and getFeeStats
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there! Just a few minor things to go!
BTW, what's the benchmark result? |
@2opremio I pasted the benchmarking here - #217 (comment) |
Benchmarking after changing the query to use sq.Select instead of raw expression:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this has gone through many many iterations but it seems we've finally landed on one that leads to quite a simple and clean implementation! LGTM from my perspective besides some tiny comments, but I'll wait for the other two to put a formal ✔️ on this one 👏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me, but I would wait on @2opremio feedback before merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job! I left a few extra comments, I am approving since I don't want to block the PR anymore, but please try the suggestions I added before merging.
What
Fixes #208 , #210
GetLedgerRange
function to query the meta table in an optimised way. This will be used by the rest of the endpoints to get the oldest and latest ledger details.GetLedgerRange
Why
Resolving bugs that were introduced with the new transactions db changes.
Known limitations
N/A